This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 22890 - It is not clear why navigator.pointerEnabled is needed
Summary: It is not clear why navigator.pointerEnabled is needed
Status: RESOLVED FIXED
Alias: None
Product: PointerEventsWG
Classification: Unclassified
Component: Pointer Events specification (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Jacob Rossi [MSFT]
QA Contact: Pointer Events Bugzilla list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-06 14:11 UTC by Olli Pettay
Modified: 2013-12-12 18:59 UTC (History)
3 users (show)

See Also:

Attachments

Description Olli Pettay 2013-08-06 14:11:24 UTC 
if (window.PointerEvent) {
  ...
} else {
  // use mouse events
}

should work just fine.
Comment 1 Sangwhan Moon 2013-08-06 14:19:54 UTC 
+1. Unless absolutely necessary tacking more properties on navigator should be avoided.
Comment 2 Arthur Barstow 2013-09-10 17:02:01 UTC 
The Pointer Events WG discussed this bug on 10-Sep-2013 and the minutes from that discussion are <http://www.w3.org/2013/09/10-pointerevents-minutes.html#item04>.
Comment 3 Jacob Rossi [MSFT] 2013-12-12 18:59:21 UTC 
Per 11/19 telecon resolution [1], I have removed pointerEnabled from the latest Editor's Draft [2].

[1]http://www.w3.org/2013/11/19-pointerevents-minutes.html#item04
[2] https://dvcs.w3.org/hg/pointerevents/raw-file/c16e5fe3ff87/pointerEvents.html